Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1622

reference: 941-tree-1
name: 1622
tree-preservation-order: undefined
941-tpo-1
uprn
address-text
point: POINT (-0.994521 50.857247)
geometry: MULTIPOLYGON (((-0.994478 50.857242,-0.994480 50.857251,-0.994486 50.857258,-0.994495 50.857264,-0.994507 50.857268,-0.994520 50.857270,-0.994534 50.857269,-0.994546 50.857265,-0.994555 50.857259,-0.994561 50.857251,-0.994564 50.857243,-0.994562 50.857235,-0.994556 50.857227,-0.994546 50.857221,-0.994535 50.857217,-0.994522 50.857216,-0.994508 50.857217,-0.994496 50.857221,-0.994487 50.857227,-0.994481 50.857234,-0.994478 50.857242)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL